[Backport] Change stack version requirements due to the breaking changes#15273
[Backport] Change stack version requirements due to the breaking changes#15273rdner wants to merge 2 commits intoelastic:backport-elastic_agent-2.5from
Conversation
rdner
added
Team:Elastic-Agent
rdner
changed the title
VihasMakwana
left a comment
VihasMakwana
left a comment
There was a problem hiding this comment.
LGTM, just a minor nit.
|
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
jsoriano
left a comment
jsoriano
left a comment
There was a problem hiding this comment.
We should revert the breaking change on this branch, and keep the previous kibana constraint, so the fix reaches affected installations.
rdner
force-pushed
the
change-stack-version-requirements-2.5
branch
from
d88d109 to
4e230a9
Compare
|
After discussing this with @cmacknz we make a decision to close this PR. The stack constraint wouldn't prevent the original issue. This stack constraint does not control the Elastic Agent version and the breaking change took place in Elastic Agent, not in the stack itself. |
|
💚 Build Succeeded
History
cc @rdner |
4 participants
Proposed commit message
The metric name
queue.filled.pct.eventswas changed toqueue.filled.pctin v8.15.0 by this commit elastic/beats@f8aedce (PR elastic/beats#39774).We've fixed the metric name in the package fields by this PR #15244
However, the minimal stack version requirements remained unchanged. This would break any customers running on stack versions 8.11.2 – 8.14.3 and upgrading their Elastic Agent integration to 2.5.2.
Checklist
changelog.ymlfile.- [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practicesRelated issues